App Review

RSS for tag

App review is the process of evaluating apps and app updates submitted to the App Store to ensure they are reliable, perform as expected, and follow Apple guidelines.

Posts under App Review tag

200 Posts

Post

Replies

Boosts

Views

Activity

Handling ITMS-91061: Missing privacy manifest
An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest
0
0
8.2k
Mar ’25
No reviewer reply in Resolution Center after 4th rejection (Apple ID 1043931945|1)
I first submitted my new app with Apple ID 1043931945|1, on September 17th 2026 — since then I have had 4 rejections, with some response times taking 12 - 14 days. On each of the first 3 rejections I corrected whatever needed to be corrected within 48 hours. I submitted the most recent fixes (rejection #3) on October 3rd and received a 4th rejection on October 13th. This rejection, 2.1 App Completeness, is I believe a reviewer error. I also flagged this with Case ID: 102990507478 The reviewer — in their message in resolution center, stated that they could not move past a certain screen in the app — I replied in the thread in resolution center same day and the following day uploaded a video of me navigating the app from beginning to end, including the screen they mentioned they could not progress past. In the body of the message I then explained they should have tapped the text "tap when done", which would fade up the next user prompt as demonstrated in the uploaded video. Rejection #4 is dated 13 October @ 4:54 pm; it is now 17 October and as yet no reply in the thread. I thought replying in the thread in resolution center would yield a reasonable response time, but so far nothing and I am not sure how many days I am supposed to sit tight for. It has already been a month of submissions and re-submissions. Furthermore, as I do not think there is anything to fix this time around I'm stuck. I urgently need the reviewer or a reviewer to look at the video posted in the thread and give feedback as to whether this is indeed an error or if I am missing something. Any assistance here would be very much appreciated. Thank you.
2
0
159
19s
APP Review Question
I submitted my first APP for review and it was rejected. Below is what they said. I have tested this APP on every simulator I can find, but I can't find an iPad Air Gen 5 with iOS 27. iOS 26.5 is the best I can find. But every device I test it on, it works just fine. I have asked for more clarification, because I don't know what to do now. Any advice or assistance would be appreciated. Bug description: We were unable to use any core feature, because no further action occurred when we were tapping any option/feature. Review device details: Device type: iPad Air (5th generation) OS version: iPadOS 27.0 Internet Connection: Active
1
0
402
1m
Help with my AppReview
Hey Apple Developers! I am about to release my first iOS Application, but I am having a hard time with the app reviews. Here some curiosities I just don't understand. Hopefully you can tell me why the app was rejected and what I have to do in order to make it work... Review A: Apple first responded with: Guideline 2.5.4 - Performance - Software Requirements Due to the usage of Bluetooth Low Energy and the Core Bluetooth framework and Guideline 2.1 - Information Needed The App Tracking Transparency permission request, due to the usage of Ad frameworks. So I created a video in which I explained why I need it and anotherone where the ATT dialog appears. (since I am from germany, I even used a VPN to "simulate" the appearance of the ATT Dialog in the US, since in the EU dialog this looks a bit different. The EU version of it was visible in the initial video I provided. After that (still same request ID) it got rejected because the IAP was missing in the review request, even though it was in there. BLE and ATT wasn't a problem anymore I thought, well may be they've overseen the IAP, so I created a complete new request, uploaded a new (further developed) application. No changes on the IAP, ATT nor BLE parts. Review B: Again this was declined, for the same reasons review A was declined the first time. I explained EXACTLY the same thing, as in review A. The only answer was: We appreciate your efforts to comply with the App Review Guidelines. Please resubmit the app for review in App Store Connect once any necessary adjustments have been made. We look forward to reviewing your resubmitted app. I thought: Well, may be it's not possible to approve an app that was once declined (as mentioned this is my first review) So I created a new review request. Review C: Including a new video for the app itself (I was had developed some progress already) and the BLE video again (to prove the usage of CBPeripheralManager and CBCentralManager) It got decline AGAIN. Reasons: Guideline 2.5.4 - Performance - Software Requirements BLE again Guideline 5.1.2(i) - Legal - Privacy - Data Use and Sharing ATT Problem again. Again, explained where to find it and even provided timestamps for the videos on where to find the ATT. (There were 2 reviews upfront this story without the Ad/ATT part already, that's why I wrote "...5th request") I am very frustrated right now and I have no clue what I am supposed to do here. It might be that I am doing something wrong here (as mentioned, first apple review), but please, let me know what that is!
1
0
166
3m
First app stuck in Waiting for Review since Nov 11 despite approved expedite
Hello, My PLNR (Apple ID 6820005956), iOS 1.0, has been in Waiting for Review since November 11 with no movement. I responded to App Review’s last message the same day. Expedited review was approved on November 10, and I requested it again on November 16. There are no outstanding messages or required actions in App Store Connect. Support case: 30000019700993 Could someone from App Review check whether this submission is stuck? Thank you.
0
0
7
9m
Developer Program Enrollment- RBSLL32M84
Dear Apple Developer Program Support Team, I am writing regarding our Apple Developer Program organization enrollment, which has remained in "under review" status for an almost a month. Enrollment Details: Organization Name: YATRAB2B PRIVATE LIMITED Enrollment ID: RBSLL32M84 Account Email: consultantdaya@gmail.com We have completed all initial steps on our end and are eager to proceed with publishing our applications on the App Store. Could you please review our application status and let us know if any additional documentation, D-U-N-S verification details, or a verification phone call is required from our authorized signatory? We have already submitted all the documents whic are required to you. please let us know how we can get the clearance from your end asap. Thank you
0
0
9
42m
TestFlight external Beta App Review fails with HTTP 422 across multiple apps on the same developer team
Hi everyone, I’m unable to submit builds for external TestFlight testing across multiple iOS apps on the same Apple Developer team. The builds upload successfully, but clicking “Submit for Review” in App Store Connect fails before the build enters Beta App Review. Here’s one example I reproduced and captured in Chrome DevTools: App: Benny Wallet App Apple ID: 6834886147 iOS version and build: 0.3.1 (104) Build status: Ready to Submit Request: POST /iris/v1/betaAppReviewSubmissions Response: HTTP 422 ENTITY_UNPROCESSABLE Error message: “There was an error processing your request. Please try again later.” Both the Free Apps and Paid Apps agreements show as active. I reproduced the error with “Automatically notify testers” turned off as well. Other apps on the same team show the same submission error in the UI. This looks similar to the reports in https://developer.apple.com/forums/thread/857429. Has anyone with the same HTTP 422 across multiple apps managed to get external TestFlight submissions working again? If so, what fixed it? If someone from the App Store Connect or TestFlight team is able to look into this, could you check whether there’s an issue with our team’s beta distribution authorization or Beta Contract association? I’ve filed Feedback Assistant report FB25625640. I can provide the Apple request UUID and UTC timestamp through that report if needed. Thanks, Frank
0
0
24
3h
iOS submission stuck in Waiting for Review since 10 November
Hello, Please check this submission. It has been in Waiting for Review since 10 November 2026, 11:35 (UTC+5) and has not moved to In Review. There are no messages in App Review. App: Спец GO Apple ID: 6744580177 Bundle ID: com.shvaiberovas.sgc Team ID: 44XR7LBDP2 Platform: iOS Version / build: 1.3.1 (56) Submission ID: 66760f89-baa4-49b4-ac7b-b0996a125a9c Submitted: 10 November 2026, 11:35 (UTC+5) Status: Waiting for Review This is the first release. An earlier submission was rejected once; this build was sent after that. Replacing the build, metadata, or version did not start review, so this submission has not been cancelled or replaced. A companion performer app on the same team is already approved and live. This binary is the customer app for the same service. Could someone from App Review confirm the submission is in the queue, or contact us in App Store Connect if something else is required? We will not upload another build unless asked. Thank you.
0
0
25
3h
2 months for first review, rejection over one word, no Support replies, impossible document request
Hello, I'd like to share my experience as an independent developer and ask Apple staff to look into it, because it seems to be a process problem rather than a single mistake. First review took two months. My first app was under review for about two months. The reviewer replied every 7–10 days, each time with one small issue, and sent the app back. I fixed everything, but it would have taken days instead of months if all issues had been listed at once. Is there a reason App Review cannot report all found issues in one message? Update rejected over one word. After approval I submitted an update. It was reviewed the next day and rejected because of the phrase "psychoactive substances". The app helps people QUIT using them. It seems the reviewer did not read the description and assumed the app promotes use. The update has now been "in review" for 10 days. Developer Support does not respond. SMS verification codes stopped arriving to my phone number, so we agreed with Support to change the number. I was supposed to receive instructions between the 8th and the 13th. No useful reply came until I wrote a more direct message, and now there has been no answer to that for 4 days. At the same time, I receive unnecessary promotional emails from Apple several times a day. Answers to real cases never come, but marketing emails arrive every day. Document verification. I have a D-U-N-S number. It is used for my Google Play account and for advertising. To get it, a business is checked against official government registries. Despite this, I was asked for documents in a language that is not used for any official, business or banking paperwork in my country. A notary cannot certify a document that is not in the state language, so the request cannot be fulfilled as asked. Why is a verified D-U-N-S number not enough? And how can documents in a language spoken by about 250 million people not be accepted? Compensation. I asked for compensation for the two months of membership I could not use for its purpose (publishing my app). There has been no reply. Region. Looking at developer forums and communities, I see very few complaints like these from developers in the US, while developers from Asia and Central Asia describe the same long delays, silence and document problems. I may be wrong, but from the outside it looks like developers from our region are treated differently. I would like to understand why. For comparison: on Google Play my apps were published in 1–3 days and updates are reviewed within hours (24 hours at most). I understand App Review handles a huge volume, and I respect the work. But long silences, one-issue-at-a-time feedback and rejections that don't reflect the app's actual purpose make it very hard for small developers. I would really appreciate it if someone from Apple could review my cases. I can provide the app ID and support case numbers to Apple staff on request. Thank you.
0
0
24
4h
Update waiting for review since Nov 18 — kindly asking for a look
Hello App Review team, We are a very small indie team behind Pop! Jelly PangPang (Apple ID 6817233245). Our update 1.0.59 (build 54) was submitted on Nov 18 at 07:59 KST and is currently Waiting for Review. We have also sent an expedited review request and a status inquiry (case 30000019261223). This update contains bug fixes and newly redesigned stages 1 to 5, so it matters a lot to our existing players. We completely understand how busy the team is. If someone could take a look whenever possible, we would be deeply grateful. Thank you very much for your time and for everything you do for developers. Kind regards, The Jelly PangPang team
0
0
14
4h
DSA trader verification stuck: SMS code never arrives to Ukrainian number (Case 102999512585)
Hello, I'm an individual developer (sole proprietor / FOP, Ukraine) and I'm trying to complete the Digital Services Act trader status in App Store Connect so my app can be distributed in the EU storefronts. Status Trader e-mail address: verified successfully. Trader phone number: verification is blocked. The SMS verification code never arrives. I tried two different Ukrainian numbers (lifecell, +380 73 …) several times over several days. Other services deliver SMS to these numbers without problems. What I've already done Opened a case with Developer Support: Case ID 102999512585. On 2026-10-21 I asked for manual verification of the phone number listed in the official Ukrainian state register (USR), and offered supporting documents: the official USR statement for my sole proprietorship (it shows the same phone number), the registration extract, and English translations of both. My app (Apple ID 6824529916) and its in-app purchases are already submitted for review, so the DSA status is the only thing preventing EU availability. Request Could someone from the App Store Connect / Developer Support team please look at Case 102999512585 and either: verify the phone number manually based on the documents above, or send the verification code by a voice call, or tell me which alternative verification method is accepted? I can provide any documents right away, and I'm available by e-mail or phone call at any time. Thank you!
2
0
214
4h
Repeated App Store Rejections Under Guideline 4.3(a) Despite Following Apple's Instructions – Seeking Advice
ello everyone, I'm looking for advice from developers who have experienced repeated App Store rejections under Guideline 4.3(a), particularly in situations involving a previously published version of the same organization's application under another developer account. I'm developing and publishing an officially authorized application for Arise and Shine Heavenly Embassy. Unfortunately, I've been caught in a prolonged App Review process, and I'm struggling to find a clear path toward resolving the issue. Background There was a previous Arise & Shine application published under a former developer's Apple Developer account. I subsequently developed a new version of the application under my own Apple Developer account, with authorization from the organization. During the review process, Apple repeatedly rejected the new application under Guideline 4.3(a) – Spam. I understand Apple's concerns about duplicate applications and appreciate the need to maintain quality on the App Store. However, I have been trying to resolve this matter in good faith. What I've done so far Communicated with Apple App Review regarding the rejection. Attended a discussion with an Apple representative to understand the concerns. Followed the instructions to investigate and remove the previous application. Accessed the former developer's account and attempted to remove the previous application. Discovered that the removal could not be completed because the former developer's Apple Developer Program membership had expired. Explained this limitation to Apple and provided supporting evidence. Was subsequently encouraged to resubmit the application, which I did in good faith. Unfortunately, the application was rejected again under the same guideline. What makes this particularly difficult is that I still haven't received a sufficiently specific explanation of what exactly is triggering Guideline 4.3(a), or what concrete changes Apple expects me to make. Where I need help I would appreciate insights from developers who have experienced similar situations. Specifically: Can an application be rejected under Guideline 4.3(a) because a previous version of the same organization's app remains on the App Store under another developer account? If the previous developer's membership has expired and the application cannot be removed through that account, what is the appropriate process for resolving this? Is there an established procedure for transferring an application or resolving duplicate-app concerns when the original developer account is no longer active? How can a developer get a case escalated to an App Review specialist who can examine the complete history of previous discussions and submissions? I have also requested another phone call with App Review because I believe a direct discussion would be more productive than continuing through repeated rejections without specific guidance. What I'm hoping to achieve I am not asking Apple to overlook its guidelines or grant special treatment. I simply want to understand the precise issue, follow the appropriate procedure, and get this officially authorized application reviewed on its actual merits. I've invested considerable time and resources into this project, and it is frustrating to remain stuck despite making genuine efforts to cooperate. If anyone from the developer community has navigated a similar situation, I would genuinely appreciate hearing how you resolved it. Thank you.
0
0
10
5h
App submission stuck in "Waiting for Review" after responding to additional IAP price verification
Hello, I'm experiencing an issue with the App Review process for my first iOS application, and I'd appreciate some guidance. Submission details: Platform: iOS App version: 1.0.0 Build: 2 Submission date: November 12, 2026, at 3:47 PM Current status: Waiting for Review Items submitted: 1 app version and 7 in-app purchases Timeline: On November 12 at 3:40 PM, I received an automated message from App Review stating that additional verification was required before the review could continue. Specifically, Apple requested confirmation that the intended prices of three consumable in-app purchases were correct. At 3:45 PM, I replied through App Store Connect confirming all three prices and providing additional clarification regarding regional pricing in the review screenshots. The submission is recorded as submitted at 3:47 PM on the same day. As of November 18, the submission and all seven in-app purchases remain in "Waiting for Review." There have been no further messages or status updates. My questions: Does replying to an additional verification request automatically allow the review to continue, or is another action required? Is it normal for a submission to remain in "Waiting for Review" for this long after providing the requested information? Is there a way to follow up directly with App Review when no reply option is available on the submission page? I've attempted to contact Developer Support but haven't received a resolution. I submited the expedite review request, but no response. Since the pask week I have created 3 email and phone call support requests, but no response I don't want to cancel or resubmit unnecessarily, especially since the app has already been waiting for almost a week. Any guidance would be greatly appreciated. Thank you.
2
3
134
5h
App Stuck in 'Waiting for Review' for over a week
Hello, My app has been stuck entirely in the "Waiting for Review" queue for over a week now. We previously received a rejection requesting specific videos and information updates. We fully updated all requested and replied message with video attachments that was requested to be uploaded on the and after I made all the necessary updates I resubmitted it. The dashboard correctly says "Waiting for Review", but nothing has happened for over a week now. We have reached out via standard developer support but have received zero responses. Our UK launch is completely paralyzed. Could an Apple forum moderator or engineer please get back to me regarding this. Case ID: 102989660047 The app was supposed to launch next week but I got feeling it wont. Apple were very quick to reject it, taking less than 24 hours, but ever since I provided everything they asked for and made all the required changes, it hasn’t even been reviewed. Honestly, it makes me want to cancel the submission and resubmit it, especially since I’ve already fixed everything they told me to. Has anyone tried this before?
1
0
200
6h
App stuck in "Waiting for Review" for 9 days – No response after two support requests
Hello Apple Developer Community and App Review Team, Our first iOS app, Infini Events, has been stuck in "Waiting for Review" since November 9, 2026. App details: App Name: Infini Events Apple ID: 6830859578 Version: 1.4.0 (Build 2) Submission Date: November 9, 2026 Current Status: Waiting for Review We have provided all the additional information requested under Guideline 2.1, including a screen recording, demo account credentials, and detailed review notes. We have already contacted Apple Developer Support twice, but the review status has not changed. This delay is affecting our planned product launch and business operations. Could an Apple representative please investigate our submission and help us understand whether any further action is required? Thank you for your assistance.
0
0
15
6h
YAZA Property App Store Review Took 1 Month, but the Next Review Took Just 1 Day – Lessons Learned
Hello Apple Developer Community, After a long journey, I'm happy to share that YAZA Property, our AI-powered real estate platform in Thailand, is officially available on the App Store! However, I want to share one important lesson from our App Store review experience that might help other developers planning their first launch. Our App Review Experience First App Review: Approximately 1 month waiting for review. Review After First Approval: Approximately 1 day. Current Status: Successfully launched on the App Store. What I Learned One of my biggest mistakes was waiting until nearly every planned feature was developed before starting the App Store submission process. If I could start again, I would approach it differently. Instead of waiting until 100% of our product roadmap was complete, I would prepare a smaller, fully functional MVP with perhaps just 10% of our planned features, submit that version for review, and continue developing future features separately. Of course, the submitted version must be complete, stable, and compliant with Apple's App Review Guidelines. My biggest takeaway: Don't confuse completing your entire product roadmap with preparing a complete, review-ready app. In our experience, the first review took approximately one month, while a subsequent review after our initial approval took only one day. I understand that review times vary, and this is only our experience, not a guaranteed timeline. Finally, We're Live! YAZA Property is now officially available on the Apple App Store. I'm curious to hear from other developers: Did your first App Store review take significantly longer than your subsequent updates? I'd love to learn from your experiences. Thank you, Apple Developer Community!
0
0
23
6h
My App is In-Review Stage for 1 Week
Hello, I have been developing and publishing applications for the Apple ecosystem for about 3–4 years. This is the first time I have encountered such a situation. A game I submitted has been stuck in the "In Review" stage since Friday—that is, for the past 6–7 days. I have sent emails requesting an expedited review and seeking clarification on what is happening, but I have received no response. Typically, the Apple team has been quite prompt in replying to my inquiries. The game I submitted is very simple, and the review process should, in theory, be quick. I have also repeatedly checked to ensure there are no pending agreements that I might have failed to accept. I am posting here as a last resort. It seems that, perhaps due to the influx of AI-generated apps, Apple may have extended its approval timeline from the usual 2 days to 10 days. Interestingly, the same game was approved by the Google Play Store within 48 hours—a rather surprising turn of events. I have attached screenshots of the "In Review" status below. Best regards,
0
0
13
6h
Significantly Delayed App Review
Hi all, Like others my app submission has been stuck in “waiting for review” for weeks. I know initial app reviews take longer than updates, but this has been delayed far too long and makes me concerned about repeating the process in the future. I submitted this app for review back on Feb 10. It was initially rejected for a minor issue, which I resolved and resubmitted the same day. After that, the build remained in “Waiting for Review” for about two weeks with no further communication. At that point I canceled the submission and resubmitted the build, thinking it may have been stuck in the queue (I now know not to do this next time). Unfortunately the new submission has also been waiting for review for another 9 days now with no messages or updates. I’ve contacted app review support as well (case ID- 102826632729). I understand review times can vary, but delays like this make it difficult for developers to plan launches or push updates when the review process is the only path to distributing apps. As paying members of the Apple Developer Program, we rely heavily on this pipeline functioning reliably. Hoping this post will reach someone from Apple who can help move the process along. If any other devs have suggestions/tips that have worked for them, please share so others in this position can become unblocked. Thanks in advance.
27
20
5.1k
6h
Mac app stuck in "Waiting for Review" for over 10 days
My Mac app Media Toolkit has been in "Waiting for Review" since 7 November 2026 (more than 10 days), and the status hasn't changed. Submission details App: Media Toolkit Platform: macOS (Mac App Store) Version / Build: 1.0 (1) Bundle ID: in.todomist.mediatoolkit.mac Submitted: 7 November 2026 Type: first submission of a new app What I've checked There are no messages or requests in App Store Connect or the Resolution Center Agreements, tax and banking are all active No other version has been submitted since Has anyone else seen long waits for macOS submissions recently? Is there anything I should check on my side? If someone from App Review sees this, I'd be grateful if you could look at the submission.
0
0
11
6h
New App Rejected Under Guideline 4.3(a) on Both iOS and tvOS — Seeking Clarification
Hi everyone, I’d like to share my experience with the first release of my app and ask for some guidance. Submission details App ID: 6829444660 Platforms: iOS and tvOS (Apple TV) Initially submitted: November 1, 2026, at 7:17 PM Rejection received: November 13, 2026, at 9:30 PM Rejection reason: Guideline 4.3(a) — Design — Spam Both the iOS and Apple TV submissions received the same rejection at the same time. How the app was built I personally developed the app using UIKit, with some parts built in SwiftUI. I also created the visual assets myself using Canva. AI was not involved in writing or designing the app; its involvement was limited to testing-related assistance. Having personally worked on the implementation and visual design, it was discouraging to see the app classified as spam. I believe there may be a misunderstanding about my submission, and I would appreciate an opportunity to clarify it. What I’m asking for Could an Apple representative help identify the specific elements or duplication concerns that led to this rejection? Clear, actionable feedback would help me understand: Which aspects of the app raised concerns under Guideline 4.3(a). What changes, if any, are needed to address those concerns. What supporting information I can provide to help clarify the situation. This project means a lot to me. I respect the review process and want to meet Apple’s requirements. I would sincerely appreciate a reconsideration of my submission and clear guidance on how to move forward. Has anyone experienced a simultaneous 4.3(a) rejection on iOS and tvOS and successfully resolved it? Thank you for taking the time to read this. Any guidance would mean a great deal to me.
1
0
128
15h
iOS 1.0 in "Waiting for Review" since Nov 11 after an Information Needed resubmission (expedite accepted, macOS approved)
Hello, Our iOS app DashNovel (Apple ID 6814248100) has been in "Waiting for Review" since Nov 11, and I would like to confirm that the submission is correctly queued. Timeline (Pacific Time): Nov 10, 3:35 PM: Submitted iOS 1.0 (build 26) together with our first subscription group and two auto-renewable subscriptions (monthly and yearly). Nov 10, about 9:06 PM: Received "Guideline 2.1 - Information Needed - New App Submission". The same day, we added the requested screen recording and details to App Review Information and resubmitted. Nov 11: We removed the submission from review to switch to build 27 (the only change: Restore Purchases now shows a result alert), then resubmitted at 12:33 AM together with the subscription group and both subscriptions. Submission ID: b717efcf-1390-4c4b-800b-c2022e1291fd Nov 13: Requested expedited review for iOS and macOS. Both requests were accepted. Nov 13, about 4:40 PM: macOS 1.0 (the same build 27, submitted at the same time) was approved after about 10 minutes in review. As of today: iOS 1.0 is still "Waiting for Review". There are no messages in App Store Connect, and the earlier Information Needed thread no longer has a reply option. Developer Support (case 30000006277096) confirmed the status and said no further action is needed if an expedite was requested. Because the subscriptions were submitted with the iOS version, we are holding the approved macOS release until the iOS version is reviewed. Could someone from App Review please check whether this submission is correctly in the expedited queue, and let us know if anything is needed from our side? We are happy to provide anything further. Thank you.
0
0
132
16h
Handling ITMS-91061: Missing privacy manifest
An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest
Replies
0
Boosts
0
Views
8.2k
Activity
Mar ’25
No reviewer reply in Resolution Center after 4th rejection (Apple ID 1043931945|1)
I first submitted my new app with Apple ID 1043931945|1, on September 17th 2026 — since then I have had 4 rejections, with some response times taking 12 - 14 days. On each of the first 3 rejections I corrected whatever needed to be corrected within 48 hours. I submitted the most recent fixes (rejection #3) on October 3rd and received a 4th rejection on October 13th. This rejection, 2.1 App Completeness, is I believe a reviewer error. I also flagged this with Case ID: 102990507478 The reviewer — in their message in resolution center, stated that they could not move past a certain screen in the app — I replied in the thread in resolution center same day and the following day uploaded a video of me navigating the app from beginning to end, including the screen they mentioned they could not progress past. In the body of the message I then explained they should have tapped the text "tap when done", which would fade up the next user prompt as demonstrated in the uploaded video. Rejection #4 is dated 13 October @ 4:54 pm; it is now 17 October and as yet no reply in the thread. I thought replying in the thread in resolution center would yield a reasonable response time, but so far nothing and I am not sure how many days I am supposed to sit tight for. It has already been a month of submissions and re-submissions. Furthermore, as I do not think there is anything to fix this time around I'm stuck. I urgently need the reviewer or a reviewer to look at the video posted in the thread and give feedback as to whether this is indeed an error or if I am missing something. Any assistance here would be very much appreciated. Thank you.
Replies
2
Boosts
0
Views
159
Activity
19s
APP Review Question
I submitted my first APP for review and it was rejected. Below is what they said. I have tested this APP on every simulator I can find, but I can't find an iPad Air Gen 5 with iOS 27. iOS 26.5 is the best I can find. But every device I test it on, it works just fine. I have asked for more clarification, because I don't know what to do now. Any advice or assistance would be appreciated. Bug description: We were unable to use any core feature, because no further action occurred when we were tapping any option/feature. Review device details: Device type: iPad Air (5th generation) OS version: iPadOS 27.0 Internet Connection: Active
Replies
1
Boosts
0
Views
402
Activity
1m
Help with my AppReview
Hey Apple Developers! I am about to release my first iOS Application, but I am having a hard time with the app reviews. Here some curiosities I just don't understand. Hopefully you can tell me why the app was rejected and what I have to do in order to make it work... Review A: Apple first responded with: Guideline 2.5.4 - Performance - Software Requirements Due to the usage of Bluetooth Low Energy and the Core Bluetooth framework and Guideline 2.1 - Information Needed The App Tracking Transparency permission request, due to the usage of Ad frameworks. So I created a video in which I explained why I need it and anotherone where the ATT dialog appears. (since I am from germany, I even used a VPN to "simulate" the appearance of the ATT Dialog in the US, since in the EU dialog this looks a bit different. The EU version of it was visible in the initial video I provided. After that (still same request ID) it got rejected because the IAP was missing in the review request, even though it was in there. BLE and ATT wasn't a problem anymore I thought, well may be they've overseen the IAP, so I created a complete new request, uploaded a new (further developed) application. No changes on the IAP, ATT nor BLE parts. Review B: Again this was declined, for the same reasons review A was declined the first time. I explained EXACTLY the same thing, as in review A. The only answer was: We appreciate your efforts to comply with the App Review Guidelines. Please resubmit the app for review in App Store Connect once any necessary adjustments have been made. We look forward to reviewing your resubmitted app. I thought: Well, may be it's not possible to approve an app that was once declined (as mentioned this is my first review) So I created a new review request. Review C: Including a new video for the app itself (I was had developed some progress already) and the BLE video again (to prove the usage of CBPeripheralManager and CBCentralManager) It got decline AGAIN. Reasons: Guideline 2.5.4 - Performance - Software Requirements BLE again Guideline 5.1.2(i) - Legal - Privacy - Data Use and Sharing ATT Problem again. Again, explained where to find it and even provided timestamps for the videos on where to find the ATT. (There were 2 reviews upfront this story without the Ad/ATT part already, that's why I wrote "...5th request") I am very frustrated right now and I have no clue what I am supposed to do here. It might be that I am doing something wrong here (as mentioned, first apple review), but please, let me know what that is!
Replies
1
Boosts
0
Views
166
Activity
3m
First app stuck in Waiting for Review since Nov 11 despite approved expedite
Hello, My PLNR (Apple ID 6820005956), iOS 1.0, has been in Waiting for Review since November 11 with no movement. I responded to App Review’s last message the same day. Expedited review was approved on November 10, and I requested it again on November 16. There are no outstanding messages or required actions in App Store Connect. Support case: 30000019700993 Could someone from App Review check whether this submission is stuck? Thank you.
Replies
0
Boosts
0
Views
7
Activity
9m
Developer Program Enrollment- RBSLL32M84
Dear Apple Developer Program Support Team, I am writing regarding our Apple Developer Program organization enrollment, which has remained in "under review" status for an almost a month. Enrollment Details: Organization Name: YATRAB2B PRIVATE LIMITED Enrollment ID: RBSLL32M84 Account Email: consultantdaya@gmail.com We have completed all initial steps on our end and are eager to proceed with publishing our applications on the App Store. Could you please review our application status and let us know if any additional documentation, D-U-N-S verification details, or a verification phone call is required from our authorized signatory? We have already submitted all the documents whic are required to you. please let us know how we can get the clearance from your end asap. Thank you
Replies
0
Boosts
0
Views
9
Activity
42m
TestFlight external Beta App Review fails with HTTP 422 across multiple apps on the same developer team
Hi everyone, I’m unable to submit builds for external TestFlight testing across multiple iOS apps on the same Apple Developer team. The builds upload successfully, but clicking “Submit for Review” in App Store Connect fails before the build enters Beta App Review. Here’s one example I reproduced and captured in Chrome DevTools: App: Benny Wallet App Apple ID: 6834886147 iOS version and build: 0.3.1 (104) Build status: Ready to Submit Request: POST /iris/v1/betaAppReviewSubmissions Response: HTTP 422 ENTITY_UNPROCESSABLE Error message: “There was an error processing your request. Please try again later.” Both the Free Apps and Paid Apps agreements show as active. I reproduced the error with “Automatically notify testers” turned off as well. Other apps on the same team show the same submission error in the UI. This looks similar to the reports in https://developer.apple.com/forums/thread/857429. Has anyone with the same HTTP 422 across multiple apps managed to get external TestFlight submissions working again? If so, what fixed it? If someone from the App Store Connect or TestFlight team is able to look into this, could you check whether there’s an issue with our team’s beta distribution authorization or Beta Contract association? I’ve filed Feedback Assistant report FB25625640. I can provide the Apple request UUID and UTC timestamp through that report if needed. Thanks, Frank
Replies
0
Boosts
0
Views
24
Activity
3h
iOS submission stuck in Waiting for Review since 10 November
Hello, Please check this submission. It has been in Waiting for Review since 10 November 2026, 11:35 (UTC+5) and has not moved to In Review. There are no messages in App Review. App: Спец GO Apple ID: 6744580177 Bundle ID: com.shvaiberovas.sgc Team ID: 44XR7LBDP2 Platform: iOS Version / build: 1.3.1 (56) Submission ID: 66760f89-baa4-49b4-ac7b-b0996a125a9c Submitted: 10 November 2026, 11:35 (UTC+5) Status: Waiting for Review This is the first release. An earlier submission was rejected once; this build was sent after that. Replacing the build, metadata, or version did not start review, so this submission has not been cancelled or replaced. A companion performer app on the same team is already approved and live. This binary is the customer app for the same service. Could someone from App Review confirm the submission is in the queue, or contact us in App Store Connect if something else is required? We will not upload another build unless asked. Thank you.
Replies
0
Boosts
0
Views
25
Activity
3h
2 months for first review, rejection over one word, no Support replies, impossible document request
Hello, I'd like to share my experience as an independent developer and ask Apple staff to look into it, because it seems to be a process problem rather than a single mistake. First review took two months. My first app was under review for about two months. The reviewer replied every 7–10 days, each time with one small issue, and sent the app back. I fixed everything, but it would have taken days instead of months if all issues had been listed at once. Is there a reason App Review cannot report all found issues in one message? Update rejected over one word. After approval I submitted an update. It was reviewed the next day and rejected because of the phrase "psychoactive substances". The app helps people QUIT using them. It seems the reviewer did not read the description and assumed the app promotes use. The update has now been "in review" for 10 days. Developer Support does not respond. SMS verification codes stopped arriving to my phone number, so we agreed with Support to change the number. I was supposed to receive instructions between the 8th and the 13th. No useful reply came until I wrote a more direct message, and now there has been no answer to that for 4 days. At the same time, I receive unnecessary promotional emails from Apple several times a day. Answers to real cases never come, but marketing emails arrive every day. Document verification. I have a D-U-N-S number. It is used for my Google Play account and for advertising. To get it, a business is checked against official government registries. Despite this, I was asked for documents in a language that is not used for any official, business or banking paperwork in my country. A notary cannot certify a document that is not in the state language, so the request cannot be fulfilled as asked. Why is a verified D-U-N-S number not enough? And how can documents in a language spoken by about 250 million people not be accepted? Compensation. I asked for compensation for the two months of membership I could not use for its purpose (publishing my app). There has been no reply. Region. Looking at developer forums and communities, I see very few complaints like these from developers in the US, while developers from Asia and Central Asia describe the same long delays, silence and document problems. I may be wrong, but from the outside it looks like developers from our region are treated differently. I would like to understand why. For comparison: on Google Play my apps were published in 1–3 days and updates are reviewed within hours (24 hours at most). I understand App Review handles a huge volume, and I respect the work. But long silences, one-issue-at-a-time feedback and rejections that don't reflect the app's actual purpose make it very hard for small developers. I would really appreciate it if someone from Apple could review my cases. I can provide the app ID and support case numbers to Apple staff on request. Thank you.
Replies
0
Boosts
0
Views
24
Activity
4h
Update waiting for review since Nov 18 — kindly asking for a look
Hello App Review team, We are a very small indie team behind Pop! Jelly PangPang (Apple ID 6817233245). Our update 1.0.59 (build 54) was submitted on Nov 18 at 07:59 KST and is currently Waiting for Review. We have also sent an expedited review request and a status inquiry (case 30000019261223). This update contains bug fixes and newly redesigned stages 1 to 5, so it matters a lot to our existing players. We completely understand how busy the team is. If someone could take a look whenever possible, we would be deeply grateful. Thank you very much for your time and for everything you do for developers. Kind regards, The Jelly PangPang team
Replies
0
Boosts
0
Views
14
Activity
4h
DSA trader verification stuck: SMS code never arrives to Ukrainian number (Case 102999512585)
Hello, I'm an individual developer (sole proprietor / FOP, Ukraine) and I'm trying to complete the Digital Services Act trader status in App Store Connect so my app can be distributed in the EU storefronts. Status Trader e-mail address: verified successfully. Trader phone number: verification is blocked. The SMS verification code never arrives. I tried two different Ukrainian numbers (lifecell, +380 73 …) several times over several days. Other services deliver SMS to these numbers without problems. What I've already done Opened a case with Developer Support: Case ID 102999512585. On 2026-10-21 I asked for manual verification of the phone number listed in the official Ukrainian state register (USR), and offered supporting documents: the official USR statement for my sole proprietorship (it shows the same phone number), the registration extract, and English translations of both. My app (Apple ID 6824529916) and its in-app purchases are already submitted for review, so the DSA status is the only thing preventing EU availability. Request Could someone from the App Store Connect / Developer Support team please look at Case 102999512585 and either: verify the phone number manually based on the documents above, or send the verification code by a voice call, or tell me which alternative verification method is accepted? I can provide any documents right away, and I'm available by e-mail or phone call at any time. Thank you!
Replies
2
Boosts
0
Views
214
Activity
4h
Repeated App Store Rejections Under Guideline 4.3(a) Despite Following Apple's Instructions – Seeking Advice
ello everyone, I'm looking for advice from developers who have experienced repeated App Store rejections under Guideline 4.3(a), particularly in situations involving a previously published version of the same organization's application under another developer account. I'm developing and publishing an officially authorized application for Arise and Shine Heavenly Embassy. Unfortunately, I've been caught in a prolonged App Review process, and I'm struggling to find a clear path toward resolving the issue. Background There was a previous Arise & Shine application published under a former developer's Apple Developer account. I subsequently developed a new version of the application under my own Apple Developer account, with authorization from the organization. During the review process, Apple repeatedly rejected the new application under Guideline 4.3(a) – Spam. I understand Apple's concerns about duplicate applications and appreciate the need to maintain quality on the App Store. However, I have been trying to resolve this matter in good faith. What I've done so far Communicated with Apple App Review regarding the rejection. Attended a discussion with an Apple representative to understand the concerns. Followed the instructions to investigate and remove the previous application. Accessed the former developer's account and attempted to remove the previous application. Discovered that the removal could not be completed because the former developer's Apple Developer Program membership had expired. Explained this limitation to Apple and provided supporting evidence. Was subsequently encouraged to resubmit the application, which I did in good faith. Unfortunately, the application was rejected again under the same guideline. What makes this particularly difficult is that I still haven't received a sufficiently specific explanation of what exactly is triggering Guideline 4.3(a), or what concrete changes Apple expects me to make. Where I need help I would appreciate insights from developers who have experienced similar situations. Specifically: Can an application be rejected under Guideline 4.3(a) because a previous version of the same organization's app remains on the App Store under another developer account? If the previous developer's membership has expired and the application cannot be removed through that account, what is the appropriate process for resolving this? Is there an established procedure for transferring an application or resolving duplicate-app concerns when the original developer account is no longer active? How can a developer get a case escalated to an App Review specialist who can examine the complete history of previous discussions and submissions? I have also requested another phone call with App Review because I believe a direct discussion would be more productive than continuing through repeated rejections without specific guidance. What I'm hoping to achieve I am not asking Apple to overlook its guidelines or grant special treatment. I simply want to understand the precise issue, follow the appropriate procedure, and get this officially authorized application reviewed on its actual merits. I've invested considerable time and resources into this project, and it is frustrating to remain stuck despite making genuine efforts to cooperate. If anyone from the developer community has navigated a similar situation, I would genuinely appreciate hearing how you resolved it. Thank you.
Replies
0
Boosts
0
Views
10
Activity
5h
App submission stuck in "Waiting for Review" after responding to additional IAP price verification
Hello, I'm experiencing an issue with the App Review process for my first iOS application, and I'd appreciate some guidance. Submission details: Platform: iOS App version: 1.0.0 Build: 2 Submission date: November 12, 2026, at 3:47 PM Current status: Waiting for Review Items submitted: 1 app version and 7 in-app purchases Timeline: On November 12 at 3:40 PM, I received an automated message from App Review stating that additional verification was required before the review could continue. Specifically, Apple requested confirmation that the intended prices of three consumable in-app purchases were correct. At 3:45 PM, I replied through App Store Connect confirming all three prices and providing additional clarification regarding regional pricing in the review screenshots. The submission is recorded as submitted at 3:47 PM on the same day. As of November 18, the submission and all seven in-app purchases remain in "Waiting for Review." There have been no further messages or status updates. My questions: Does replying to an additional verification request automatically allow the review to continue, or is another action required? Is it normal for a submission to remain in "Waiting for Review" for this long after providing the requested information? Is there a way to follow up directly with App Review when no reply option is available on the submission page? I've attempted to contact Developer Support but haven't received a resolution. I submited the expedite review request, but no response. Since the pask week I have created 3 email and phone call support requests, but no response I don't want to cancel or resubmit unnecessarily, especially since the app has already been waiting for almost a week. Any guidance would be greatly appreciated. Thank you.
Replies
2
Boosts
3
Views
134
Activity
5h
App Stuck in 'Waiting for Review' for over a week
Hello, My app has been stuck entirely in the "Waiting for Review" queue for over a week now. We previously received a rejection requesting specific videos and information updates. We fully updated all requested and replied message with video attachments that was requested to be uploaded on the and after I made all the necessary updates I resubmitted it. The dashboard correctly says "Waiting for Review", but nothing has happened for over a week now. We have reached out via standard developer support but have received zero responses. Our UK launch is completely paralyzed. Could an Apple forum moderator or engineer please get back to me regarding this. Case ID: 102989660047 The app was supposed to launch next week but I got feeling it wont. Apple were very quick to reject it, taking less than 24 hours, but ever since I provided everything they asked for and made all the required changes, it hasn’t even been reviewed. Honestly, it makes me want to cancel the submission and resubmit it, especially since I’ve already fixed everything they told me to. Has anyone tried this before?
Replies
1
Boosts
0
Views
200
Activity
6h
App stuck in "Waiting for Review" for 9 days – No response after two support requests
Hello Apple Developer Community and App Review Team, Our first iOS app, Infini Events, has been stuck in "Waiting for Review" since November 9, 2026. App details: App Name: Infini Events Apple ID: 6830859578 Version: 1.4.0 (Build 2) Submission Date: November 9, 2026 Current Status: Waiting for Review We have provided all the additional information requested under Guideline 2.1, including a screen recording, demo account credentials, and detailed review notes. We have already contacted Apple Developer Support twice, but the review status has not changed. This delay is affecting our planned product launch and business operations. Could an Apple representative please investigate our submission and help us understand whether any further action is required? Thank you for your assistance.
Replies
0
Boosts
0
Views
15
Activity
6h
YAZA Property App Store Review Took 1 Month, but the Next Review Took Just 1 Day – Lessons Learned
Hello Apple Developer Community, After a long journey, I'm happy to share that YAZA Property, our AI-powered real estate platform in Thailand, is officially available on the App Store! However, I want to share one important lesson from our App Store review experience that might help other developers planning their first launch. Our App Review Experience First App Review: Approximately 1 month waiting for review. Review After First Approval: Approximately 1 day. Current Status: Successfully launched on the App Store. What I Learned One of my biggest mistakes was waiting until nearly every planned feature was developed before starting the App Store submission process. If I could start again, I would approach it differently. Instead of waiting until 100% of our product roadmap was complete, I would prepare a smaller, fully functional MVP with perhaps just 10% of our planned features, submit that version for review, and continue developing future features separately. Of course, the submitted version must be complete, stable, and compliant with Apple's App Review Guidelines. My biggest takeaway: Don't confuse completing your entire product roadmap with preparing a complete, review-ready app. In our experience, the first review took approximately one month, while a subsequent review after our initial approval took only one day. I understand that review times vary, and this is only our experience, not a guaranteed timeline. Finally, We're Live! YAZA Property is now officially available on the Apple App Store. I'm curious to hear from other developers: Did your first App Store review take significantly longer than your subsequent updates? I'd love to learn from your experiences. Thank you, Apple Developer Community!
Replies
0
Boosts
0
Views
23
Activity
6h
My App is In-Review Stage for 1 Week
Hello, I have been developing and publishing applications for the Apple ecosystem for about 3–4 years. This is the first time I have encountered such a situation. A game I submitted has been stuck in the "In Review" stage since Friday—that is, for the past 6–7 days. I have sent emails requesting an expedited review and seeking clarification on what is happening, but I have received no response. Typically, the Apple team has been quite prompt in replying to my inquiries. The game I submitted is very simple, and the review process should, in theory, be quick. I have also repeatedly checked to ensure there are no pending agreements that I might have failed to accept. I am posting here as a last resort. It seems that, perhaps due to the influx of AI-generated apps, Apple may have extended its approval timeline from the usual 2 days to 10 days. Interestingly, the same game was approved by the Google Play Store within 48 hours—a rather surprising turn of events. I have attached screenshots of the "In Review" status below. Best regards,
Replies
0
Boosts
0
Views
13
Activity
6h
Significantly Delayed App Review
Hi all, Like others my app submission has been stuck in “waiting for review” for weeks. I know initial app reviews take longer than updates, but this has been delayed far too long and makes me concerned about repeating the process in the future. I submitted this app for review back on Feb 10. It was initially rejected for a minor issue, which I resolved and resubmitted the same day. After that, the build remained in “Waiting for Review” for about two weeks with no further communication. At that point I canceled the submission and resubmitted the build, thinking it may have been stuck in the queue (I now know not to do this next time). Unfortunately the new submission has also been waiting for review for another 9 days now with no messages or updates. I’ve contacted app review support as well (case ID- 102826632729). I understand review times can vary, but delays like this make it difficult for developers to plan launches or push updates when the review process is the only path to distributing apps. As paying members of the Apple Developer Program, we rely heavily on this pipeline functioning reliably. Hoping this post will reach someone from Apple who can help move the process along. If any other devs have suggestions/tips that have worked for them, please share so others in this position can become unblocked. Thanks in advance.
Replies
27
Boosts
20
Views
5.1k
Activity
6h
Mac app stuck in "Waiting for Review" for over 10 days
My Mac app Media Toolkit has been in "Waiting for Review" since 7 November 2026 (more than 10 days), and the status hasn't changed. Submission details App: Media Toolkit Platform: macOS (Mac App Store) Version / Build: 1.0 (1) Bundle ID: in.todomist.mediatoolkit.mac Submitted: 7 November 2026 Type: first submission of a new app What I've checked There are no messages or requests in App Store Connect or the Resolution Center Agreements, tax and banking are all active No other version has been submitted since Has anyone else seen long waits for macOS submissions recently? Is there anything I should check on my side? If someone from App Review sees this, I'd be grateful if you could look at the submission.
Replies
0
Boosts
0
Views
11
Activity
6h
New App Rejected Under Guideline 4.3(a) on Both iOS and tvOS — Seeking Clarification
Hi everyone, I’d like to share my experience with the first release of my app and ask for some guidance. Submission details App ID: 6829444660 Platforms: iOS and tvOS (Apple TV) Initially submitted: November 1, 2026, at 7:17 PM Rejection received: November 13, 2026, at 9:30 PM Rejection reason: Guideline 4.3(a) — Design — Spam Both the iOS and Apple TV submissions received the same rejection at the same time. How the app was built I personally developed the app using UIKit, with some parts built in SwiftUI. I also created the visual assets myself using Canva. AI was not involved in writing or designing the app; its involvement was limited to testing-related assistance. Having personally worked on the implementation and visual design, it was discouraging to see the app classified as spam. I believe there may be a misunderstanding about my submission, and I would appreciate an opportunity to clarify it. What I’m asking for Could an Apple representative help identify the specific elements or duplication concerns that led to this rejection? Clear, actionable feedback would help me understand: Which aspects of the app raised concerns under Guideline 4.3(a). What changes, if any, are needed to address those concerns. What supporting information I can provide to help clarify the situation. This project means a lot to me. I respect the review process and want to meet Apple’s requirements. I would sincerely appreciate a reconsideration of my submission and clear guidance on how to move forward. Has anyone experienced a simultaneous 4.3(a) rejection on iOS and tvOS and successfully resolved it? Thank you for taking the time to read this. Any guidance would mean a great deal to me.
Replies
1
Boosts
0
Views
128
Activity
15h
iOS 1.0 in "Waiting for Review" since Nov 11 after an Information Needed resubmission (expedite accepted, macOS approved)
Hello, Our iOS app DashNovel (Apple ID 6814248100) has been in "Waiting for Review" since Nov 11, and I would like to confirm that the submission is correctly queued. Timeline (Pacific Time): Nov 10, 3:35 PM: Submitted iOS 1.0 (build 26) together with our first subscription group and two auto-renewable subscriptions (monthly and yearly). Nov 10, about 9:06 PM: Received "Guideline 2.1 - Information Needed - New App Submission". The same day, we added the requested screen recording and details to App Review Information and resubmitted. Nov 11: We removed the submission from review to switch to build 27 (the only change: Restore Purchases now shows a result alert), then resubmitted at 12:33 AM together with the subscription group and both subscriptions. Submission ID: b717efcf-1390-4c4b-800b-c2022e1291fd Nov 13: Requested expedited review for iOS and macOS. Both requests were accepted. Nov 13, about 4:40 PM: macOS 1.0 (the same build 27, submitted at the same time) was approved after about 10 minutes in review. As of today: iOS 1.0 is still "Waiting for Review". There are no messages in App Store Connect, and the earlier Information Needed thread no longer has a reply option. Developer Support (case 30000006277096) confirmed the status and said no further action is needed if an expedite was requested. Because the subscriptions were submitted with the iOS version, we are holding the approved macOS release until the iOS version is reviewed. Could someone from App Review please check whether this submission is correctly in the expedited queue, and let us know if anything is needed from our side? We are happy to provide anything further. Thank you.
Replies
0
Boosts
0
Views
132
Activity
16h